Skip to content

[AMD/ROCm] qwen3.5 fp8 mi355x SGL performance update#995

Draft
seungrokj wants to merge 5 commits intomainfrom
srok/sgl_qwen3.5_fp8
Draft

[AMD/ROCm] qwen3.5 fp8 mi355x SGL performance update#995
seungrokj wants to merge 5 commits intomainfrom
srok/sgl_qwen3.5_fp8

Conversation

@seungrokj
Copy link
Copy Markdown
Collaborator

@seungrokj seungrokj commented Apr 2, 2026

Need more testing.

This PR supersedes this previous PR #910

Regards,
Seungrok

Signed-off-by: seungrokj <seungrok.jung@amd.com>
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 2, 2026

Thanks for the contribution! For vLLM & SGLang, please ensure that your recipes is similar to the official vLLM recipes and/or the SGLang cookbook

If it is not, please create a PR first before we can merge your PR into the master branch. Let's ensure that the documentation is first class such that the entire ML community can benefit from your hard work! Thank you

1 similar comment
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 2, 2026

Thanks for the contribution! For vLLM & SGLang, please ensure that your recipes is similar to the official vLLM recipes and/or the SGLang cookbook

If it is not, please create a PR first before we can merge your PR into the master branch. Let's ensure that the documentation is first class such that the entire ML community can benefit from your hard work! Thank you

Signed-off-by: seungrokj <seungrok.jung@amd.com>
description:
- "Qwen3.5 fp8 mi355x performance update"
- "Relevant Issue: https://github.com/sgl-project/sglang/issues/19633"
pr-link: https://github.com/SemiAnalysisAI/InferenceX/pull/995
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 The new changelog entry uses a placeholder PR link pull/9xx instead of the actual PR number. Since this PR is #995, the link should be https://github.com/SemiAnalysisAI/InferenceX/pull/995. Please update perf-changelog.yaml line 1244 to fix the broken link before merging.

Extended reasoning...

The changelog entry added by this PR (perf-changelog.yaml, last entry) sets pr-link: https://github.com/SemiAnalysisAI/InferenceX/pull/9xx. This is clearly a placeholder that was never replaced with the actual PR number.

The specific code path is straightforward: the diff shows the new entry was added at the bottom of perf-changelog.yaml with pull/9xx as the PR link. This PR is #995 based on the PR metadata, so the correct value would be pull/995.

Existing placeholder entries in the file consistently use the pattern pull/XXX (all uppercase letters) when the PR number is unknown at write time — for example, entries for kimik2.5-int4-mi300x-vllm, glm5-fp8-mi355x-sglang, minimaxm2.5-fp8-h200-vllm, qwen3.5-bf16-mi325x-sglang, and qwen3.5-fp8-mi325x-sglang all use pull/XXX. The pull/9xx pattern is a non-standard variant suggesting the author partially began filling in the number (starting with the known digit 9) but left it incomplete.

The impact is a broken/invalid hyperlink in the changelog. Anyone clicking the link to trace the history of the qwen3.5-fp8-mi355x-sglang configuration change would land on a 404 page instead of this PR.

The fix is a one-character change: replace pull/9xx with pull/995 on line 1244 of perf-changelog.yaml.

Step-by-step proof:

  1. PR metadata confirms this is PR [AMD/ROCm] qwen3.5 fp8 mi355x SGL performance update #995 (<pr number="995">)
  2. The diff shows the addition of pr-link: https://github.com/SemiAnalysisAI/InferenceX/pull/9xx
  3. Navigating to https://github.com/SemiAnalysisAI/InferenceX/pull/9xx would 404 since 9xx is not a valid PR number
  4. The correct URL https://github.com/SemiAnalysisAI/InferenceX/pull/995 would point to this very PR

Signed-off-by: seungrokj <seungrok.jung@amd.com>
Signed-off-by: seungrokj <seungrok.jung@amd.com>
@seungrokj seungrokj marked this pull request as draft April 2, 2026 06:45
Signed-off-by: seungrokj <seungrok.jung@amd.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

1 participant